Computer-implemented systems and methods for transferring a return item to fulfillment centers for inventory management

ABSTRACT

Disclosed embodiments provide systems and methods related to managing inventory by transferring return items to fulfillment centers. A method for managing inventory comprises predicting a zone within a fulfillment center for storing a return item, generating identifiers, to be affixed at a tote containing at least one return item, that facilitate receiving process at the predicted fulfillment center, receiving, from a mobile device associated with a fulfillment center, the generated identifiers for the tote containing at least one return item, determining whether the tote is transferred to correct fulfillment center, and storing at least one return item contained in the tote in a database storing inventory associated with the predicted fulfillment center.

TECHNICAL FIELD

The present disclosure generally relates to computerized systems andmethods for inventory management in fulfillment centers. In particular,embodiments of the present disclosure relate to inventive andunconventional systems relate to computer-implemented systems, methods,and user interfaces for efficiently transferring a return item from areturn center to fulfillment centers.

BACKGROUND

A return process is as important as sales for online retailers. If thereturn process is challenging or leaves customers frustrated, thatnegatively can lead to losing any future sales from the frustratedcustomers. This can also lead to poor customer satisfaction, and areview from the dissatisfied customer may discourage potential salesfrom other buyers. However, the returns processing is costly toretailers in two ways. First are the shipping and handling costs. Theprocess of reversing an online order has many steps and includes thecost of the delivery as well as the many touches, each of which comeswith a labor cost, to move a return item back into inventory stored infulfillment centers. It is inevitable that the expense will reduceprofit margins. The second type of cost is more difficult to quantifybut the longer a return item stays out of circulation and is unable tosold, the less value it has and loss for the retailers.

To mitigate such problems, conventional inventory management systemstransfer a return item without defects from a return center storing thereturn item to a fulfillment center for resale. In order to transfer thereturn item from the return center, workers in the return center placeat least one return item in a pallet. The return item, placed in thepallet, is then transferred to the fulfillment center for resale. Whenthe return item arrives at the fulfillment center, it goes throughreceiving processes of a kind that new products undergo. For example,when a return item arrives at the fulfillment center, a workerassociated with the fulfillment center removes the return item from thepallet, scans a barcode attached to the return item, counts a quantityof the return item, places the return item in a tote, and scans a totebarcode associated with the tote. When the worker scans the totebarcode, the return item is stored in a database storing inventorywithin the fulfillment in the conventional management systems. Theresources, however, may be better utilized by simplifying the processesfor transferring a return item from a return center to a fulfillmentcenter and receiving the return item at the fulfillment center. Forexample, a computerized system may provide unloading/receiving processesof a fulfillment center to a return center enabling a return item toundergo unloading/receiving processes at the return center to facilitateunloading/receiving and stowing processes at the fulfillment center.

Therefore, there is a need for improved methods and systems fortransferring a return item from a return center to a fulfillment center.

SUMMARY

One aspect of the present disclosure is directed to a method formanaging inventory by transferring a return item from a return center toa fulfillment center. The method may comprise operations. The operationscomprise receiving, from a first mobile device, a return item identifierand a request for a return identifier to be affixed to a tote containingreturn items for transferring to a fulfillment center. The operationsfurther comprise predicting a zone within a predicted fulfillment centerfor stowing a return item associated with the received returnidentifier. After predicting a zone for stowing, the operations furthercomprise modifying a database to assign a return item identifier to areturn identifier and a tote identifier associated with a totecontaining at least one return item, assign the predicted zone to thetote identifier, and assign the fulfillment center and the toteidentifier to the return identifier. The operations further comprisereceiving, from a second mobile device, a return identifier and a toteidentifier. After receiving the identifiers, the operations furthercomprise retrieving, from the database, a fulfillment center assigned tothe received return identifier and a predicted zone assigned to thereceived tote identifier and comparing both against a location of thesecond mobile. Based on the comparison, the operations further comprisetransmitting a request, to the second mobile device, to stow the returnitems in the tote in the target fulfillment center when the propertransfer was processed, and modifying the database to assign a returnitem identifier assigned to the received tote identifier to a predictedzone assigned to the received tote identifier.

Another aspect of the present disclosure is directed to acomputer-implemented system for managing inventory by transferring areturn item from a return center to fulfillment centers. The computerimplemented system may include one or more memory devices storinginstructions. The computer-implemented system may also include one ormore processors configured to execute the instructions to performoperations as discussed above.

Yet another aspect of the present disclosure is directed to acomputer-implemented system for resale of a return item includingprocesses from receiving a return request to stowing a return itemassociated with the return request in a fulfillment center. The computerimplemented system may include one or more memory devices storinginstructions. The computer-implemented system may also include one ormore processors configured to execute the instructions to performoperations as discussed above. The operations further comprisereceiving, from a user device associated with a customer, a returnrequest and a reason for return, transmitting a pickup request to amobile device associated with a delivery worker to pick up a return itemassociated with the return request and deliver the return item to areturn center based on the determination, and generating a return itemidentifier if the return item is in condition of resale to be affixed tothe return item.

Other systems, methods, and computer-readable media are also discussedherein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a schematic block diagram illustrating an exemplaryembodiment of a network comprising computerized systems forcommunications enabling shipping, transportation, and logisticsoperations, consistent with the disclosed embodiments.

FIG. 1B depicts a sample Search Result Page (SRP) that includes one ormore search results satisfying a search request along with interactiveuser interface elements, consistent with the disclosed embodiments.

FIG. 1C depicts a sample Single Display Page (SDP) that includes aproduct and information about the product along with interactive userinterface elements, consistent with the disclosed embodiments.

FIG. 1D depicts a sample Cart page that includes items in a virtualshopping cart along with interactive user interface elements, consistentwith the disclosed embodiments.

FIG. 1E depicts a sample Order page that includes items from the virtualshopping cart along with information regarding purchase and shipping,along with interactive user interface elements, consistent with thedisclosed embodiments.

FIG. 2 is a diagrammatic illustration of an exemplary fulfillment centerconfigured to utilize disclosed computerized systems, consistent withthe disclosed embodiments.

FIG. 3 is an exemplary flow chart of process for generating identifiersto transfer at least one return item from a return center to fulfillmentcenter, consistent with the disclosed embodiments.

FIG. 4 is an exemplary flow chart of process for receiving a transferredreturn item at fulfillment center, consistent with the disclosedembodiments.

FIG. 5A depicts an exemplary user interface of a mobile device forrequesting a workstation identifier in the form of a barcode affixed toa workstation, consistent with the disclosed embodiments.

FIG. 5B depicts an exemplary user interface 501 of a mobile device 119Bfor requesting a return identifier in the form of a barcode (RTOBarcode) affixed to a tote, consistent with the disclosed embodiments.

FIG. 5C depicts an exemplary user interface 502 of a mobile device 119Bfor requesting a tote identifier in the form of a barcode affixed to atote, consistent with the disclosed embodiments.

FIG. 5D depicts an exemplary user interface of a mobile device fordisplaying information associated with return items associated with areturn identifier affixed to a tote, consistent with the disclosedembodiments.

FIG. 5E depicts an exemplary user interface of a mobile device fordisplaying a completion message for transferring a tote containing atleast one return item from a return center to a fulfillment center,consistent with the disclosed embodiments.

FIG. 5F depicts an exemplary user interface of a mobile device for forcequitting a process for receiving return items, consistent with thedisclosed embodiments.

FIG. 5G depicts an exemplary user interface of a mobile device fordisplaying a message when a workstation is already assigned to anothermobile device, consistent with the disclosed embodiments.

FIG. 5H depicts an exemplary user interface of a mobile device forcancelling the transmitted return identifier when mobile devicetransmitted unintended return identifier to warehouse management system,consistent with the disclosed embodiments.

FIG. 6 an exemplary flow chart of process 600 for processing a requestfor returning an item, consistent with the disclosed embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar parts.While several illustrative embodiments are described herein,modifications, adaptations and other implementations are possible. Forexample, substitutions, additions, or modifications may be made to thecomponents and steps illustrated in the drawings, and the illustrativemethods described herein may be modified by substituting, reordering,removing, or adding steps to the disclosed methods. Accordingly, thefollowing detailed description is not limited to the disclosedembodiments and examples. Instead, the proper scope of the invention isdefined by the appended claims.

Embodiments of the present disclosure are directed tocomputer-implemented systems and methods configured for managinginventories by transferring a return item to a fulfillment center. Thedisclosed embodiments provide innovative technical features thatsimplify processes for transferring a return item from a return centerto a fulfillment center. For example, the disclosed embodiments predicta fulfillment center and a zone within the fulfillment center to store areturn item, enable a worker associated with a return center to place areturn item in a tote according to a predefined rule of the predictedfulfillment center, generate identifiers to be affixed to the tote foruse with the fulfillment center, and enable workers associated with thefulfillment center to conveniently scan the generated identifiers toperform unloading and receiving processes. Moreover, the return item isalready placed in the tote, thus it reduces processes of placing atleast one return item in a pallet at the return center and placing atleast one return item from the pallet to a tote at the fulfillmentcenter.

Referring to FIG. 1A, a schematic block diagram 100 illustrating anexemplary embodiment of a system comprising computerized systems forcommunications enabling shipping, transportation, and logisticsoperations is shown. As illustrated in FIG. 1A, system 100 may include avariety of systems, each of which may be connected to one another viaone or more networks. The systems may also be connected to one anothervia a direct connection, for example, using a cable. The depictedsystems include a shipment authority technology (SAT) system 101, anexternal front end system 103, an internal front end system 105, atransportation system 107, mobile devices 107A, 107B, and 107C, sellerportal 109, shipment and order tracking (SOT) system 111, fulfillmentoptimization (FO) system 113, fulfillment messaging gateway (FMG) 115,supply chain management (SCM) system 117, warehouse management system119, mobile devices 119A, 119B, and 119C (depicted as being inside offulfillment center (FC) 200), 3^(rd) party fulfillment systems 121A,121B, and 121C, fulfillment center authorization system (FC Auth) 123,and labor management system (LMS) 125.

SAT system 101, in some embodiments, may be implemented as a computersystem that monitors order status and delivery status. For example, SATsystem 101 may determine whether an order is past its Promised DeliveryDate (PDD) and may take appropriate action, including initiating a neworder, reshipping the items in the non-delivered order, canceling thenon-delivered order, initiating contact with the ordering customer, orthe like. SAT system 101 may also monitor other data, including output(such as a number of packages shipped during a particular time period)and input (such as the number of empty cardboard boxes received for usein shipping). SAT system 101 may also act as a gateway between differentdevices in system 100, enabling communication (e.g., usingstore-and-forward or other techniques) between devices such as externalfront end system 103 and FO system 113.

External front end system 103, in some embodiments, may be implementedas a computer system that enables external users to interact with one ormore systems in system 100. For example, in embodiments where system 100enables the presentation of systems to enable users to place an orderfor an item, external front end system 103 may be implemented as a webserver that receives search requests, presents item pages, and solicitspayment information. For example, external front end system 103 may beimplemented as a computer or computers running software such as theApache HTTP Server, Microsoft Internet Information Services (IIS),NGINX, or the like. In other embodiments, external front end system 103may run custom web server software designed to receive and processrequests from external devices (e.g., mobile device 102A or computer102B), acquire information from databases and other data stores based onthose requests, and provide responses to the received requests based onacquired information.

In some embodiments, external front end system 103 may include one ormore of a web caching system, a database, a search system, or a paymentsystem. In one aspect, external front end system 103 may comprise one ormore of these systems, while in another aspect, external front endsystem 103 may comprise interfaces (e.g., server-to-server,database-to-database, or other network connections) connected to one ormore of these systems.

An illustrative set of steps, illustrated by FIGS. 1B, 1C, 1D, and 1E,will help to describe some operations of external front end system 103.External front end system 103 may receive information from systems ordevices in system 100 for presentation and/or display. For example,external front end system 103 may host or provide one or more web pages,including a Search Result Page (SRP) (e.g., FIG. 1B), a Single DetailPage (SDP) (e.g., FIG. 1C), a Cart page (e.g., FIG. 1D), or an Orderpage (e.g., FIG. 1E). A user device (e.g., using mobile device 102A orcomputer 102B) may navigate to external front end system 103 and requesta search by entering information into a search box. External front endsystem 103 may request information from one or more systems in system100. For example, external front end system 103 may request informationfrom FO System 113 that satisfies the search request. External front endsystem 103 may also request and receive (from FO System 113) a PromisedDelivery Date or “PDD” for each product included in the search results.The PDD, in some embodiments, may represent an estimate of when apackage containing the product will arrive at the user's desiredlocation or a date by which the product is promised to be delivered atthe user's desired location if ordered within a particular period oftime, for example, by the end of the day (11:59 PM). (PDD is discussedfurther below with respect to FO System 113.)

External front end system 103 may prepare an SRP (e.g., FIG. 1B) basedon the information. The SRP may include information that satisfies thesearch request. For example, this may include pictures of products thatsatisfy the search request. The SRP may also include respective pricesfor each product, or information relating to enhanced delivery optionsfor each product, PDD, weight, size, offers, discounts, or the like.External front end system 103 may send the SRP to the requesting userdevice (e.g., via a network).

A user device may then select a product from the SRP, e.g., by clickingor tapping a user interface, or using another input device, to select aproduct represented on the SRP. The user device may formulate a requestfor information on the selected product and send it to external frontend system 103. In response, external front end system 103 may requestinformation related to the selected product. For example, theinformation may include additional information beyond that presented fora product on the respective SRP. This could include, for example, shelflife, country of origin, weight, size, number of items in package,handling instructions, or other information about the product. Theinformation could also include recommendations for similar products(based on, for example, big data and/or machine learning analysis ofcustomers who bought this product and at least one other product),answers to frequently asked questions, reviews from customers,manufacturer information, pictures, or the like.

External front end system 103 may prepare an SDP (Single Detail Page)(e.g., FIG. 1C) based on the received product information. The SDP mayalso include other interactive elements such as a “Buy Now” button, a“Add to Cart” button, a quantity field, a picture of the item, or thelike. The SDP may further include a list of sellers that offer theproduct. The list may be ordered based on the price each seller offerssuch that the seller that offers to sell the product at the lowest pricemay be listed at the top. The list may also be ordered based on theseller ranking such that the highest ranked seller may be listed at thetop. The seller ranking may be formulated based on multiple factors,including, for example, the seller's past track record of meeting apromised PDD. External front end system 103 may deliver the SDP to therequesting user device (e.g., via a network).

The requesting user device may receive the SDP which lists the productinformation. Upon receiving the SDP, the user device may then interactwith the SDP. For example, a user of the requesting user device mayclick or otherwise interact with a “Place in Cart” button on the SDP.This adds the product to a shopping cart associated with the user. Theuser device may transmit this request to add the product to the shoppingcart to external front end system 103.

External front end system 103 may generate a Cart page (e.g., FIG. 1D).The Cart page, in some embodiments, lists the products that the user hasadded to a virtual “shopping cart.” A user device may request the Cartpage by clicking on or otherwise interacting with an icon on the SRP,SDP, or other pages. The Cart page may, in some embodiments, list allproducts that the user has added to the shopping cart, as well asinformation about the products in the cart such as a quantity of eachproduct, a price for each product per item, a price for each productbased on an associated quantity, information regarding PDD, a deliverymethod, a shipping cost, user interface elements for modifying theproducts in the shopping cart (e.g., deletion or modification of aquantity), options for ordering other product or setting up periodicdelivery of products, options for setting up interest payments, userinterface elements for proceeding to purchase, or the like. A user at auser device may click on or otherwise interact with a user interfaceelement (e.g., a button that reads “Buy Now”) to initiate the purchaseof the product in the shopping cart. Upon doing so, the user device maytransmit this request to initiate the purchase to external front endsystem 103.

External front end system 103 may generate an Order page (e.g., FIG. 1E)in response to receiving the request to initiate a purchase. The Orderpage, in some embodiments, re-lists the items from the shopping cart andrequests input of payment and shipping information. For example, theOrder page may include a section requesting information about thepurchaser of the items in the shopping cart (e.g., name, address, e-mailaddress, phone number), information about the recipient (e.g., name,address, phone number, delivery information), shipping information(e.g., speed/method of delivery and/or pickup), payment information(e.g., credit card, bank transfer, check, stored credit), user interfaceelements to request a cash receipt (e.g., for tax purposes), or thelike. External front end system 103 may send the Order page to the userdevice.

The user device may enter information on the Order page and click orotherwise interact with a user interface element that sends theinformation to external front end system 103. From there, external frontend system 103 may send the information to different systems in system100 to enable the creation and processing of a new order with theproducts in the shopping cart.

In some embodiments, external front end system 103 may be furtherconfigured to enable sellers to transmit and receive informationrelating to orders.

Internal front end system 105, in some embodiments, may be implementedas a computer system that enables internal users (e.g., employees of anorganization that owns, operates, or leases system 100) to interact withone or more systems in system 100. For example, in embodiments wherenetwork 101 enables the presentation of systems to enable users to placean order for an item, internal front end system 105 may be implementedas a web server that enables internal users to view diagnostic andstatistical information about orders, modify item information, or reviewstatistics relating to orders. For example, internal front end system105 may be implemented as a computer or computers running software suchas the Apache HTTP Server, Microsoft Internet Information Services(IIS), NGINX, or the like. In other embodiments, internal front endsystem 105 may run custom web server software designed to receive andprocess requests from systems or devices depicted in system 100 (as wellas other devices not depicted), acquire information from databases andother data stores based on those requests, and provide responses to thereceived requests based on acquired information.

In some embodiments, internal front end system 105 may include one ormore of a web caching system, a database, a search system, a paymentsystem, an analytics system, an order monitoring system, or the like. Inone aspect, internal front end system 105 may comprise one or more ofthese systems, while in another aspect, internal front end system 105may comprise interfaces (e.g., server-to-server, database-to-database,or other network connections) connected to one or more of these systems.

Transportation system 107, in some embodiments, may be implemented as acomputer system that enables communication between systems or devices insystem 100 and mobile devices 107A-107C. Transportation system 107, insome embodiments, may receive information from one or more mobiledevices 107A-107C (e.g., mobile phones, smart phones, PDAs, or thelike). For example, in some embodiments, mobile devices 107A-107C maycomprise devices operated by delivery workers. The delivery workers, whomay be permanent, temporary, or shift employees, may utilize mobiledevices 107A-107C to effect delivery of packages containing the productsordered by users. For example, to deliver a package, the delivery workermay receive a notification on a mobile device indicating which packageto deliver and where to deliver it. Upon arriving at the deliverylocation, the delivery worker may locate the package (e.g., in the backof a truck or in a crate of packages), scan or otherwise capture dataassociated with an identifier on the package (e.g., a barcode, an image,a text string, an RFID tag, or the like) using the mobile device, anddeliver the package (e.g., by leaving it at a front door, leaving itwith a security guard, handing it to the recipient, or the like). Insome embodiments, the delivery worker may capture photo(s) of thepackage and/or may obtain a signature using the mobile device. Themobile device may send information to transportation system 107including information about the delivery, including, for example, time,date, GPS location, photo(s), an identifier associated with the deliveryworker, an identifier associated with the mobile device, or the like.Transportation system 107 may store this information in a database (notpictured) for access by other systems in system 100. Transportationsystem 107 may, in some embodiments, use this information to prepare andsend tracking data to other systems indicating the location of aparticular package.

In some embodiments, certain users may use one kind of mobile device(e.g., permanent workers may use a specialized PDA with custom hardwaresuch as a barcode scanner, stylus, and other devices) while other usersmay use other kinds of mobile devices (e.g., temporary or shift workersmay utilize off-the-shelf mobile phones and/or smartphones).

In some embodiments, transportation system 107 may associate a user witheach device. For example, transportation system 107 may store anassociation between a user (represented by, e.g., a user identifier, anemployee identifier, or a phone number) and a mobile device (representedby, e.g., an International Mobile Equipment Identity (IMEI), anInternational Mobile Subscription Identifier (IMSI), a phone number, aUniversal Unique Identifier (UUID), or a Globally Unique Identifier(GUID)). Transportation system 107 may use this association inconjunction with data received on deliveries to analyze data stored inthe database in order to determine, among other things, a location ofthe worker, an efficiency of the worker, or a speed of the worker.

Seller portal 109, in some embodiments, may be implemented as a computersystem that enables sellers or other external entities to electronicallycommunicate with one or more systems in system 100. For example, aseller may utilize a computer system (not pictured) to upload or provideproduct information, order information, contact information, or thelike, for products that the seller wishes to sell through system 100using seller portal 109.

Shipment and order tracking system 111, in some embodiments, may beimplemented as a computer system that receives, stores, and forwardsinformation regarding the location of packages containing productsordered by customers (e.g., by a user using devices 102A-102B). In someembodiments, shipment and order tracking system 111 may request or storeinformation from web servers (not pictured) operated by shippingcompanies that deliver packages containing products ordered bycustomers.

In some embodiments, shipment and order tracking system 111 may requestand store information from systems depicted in system 100. For example,shipment and order tracking system 111 may request information fromtransportation system 107. As discussed above, transportation system 107may receive information from one or more mobile devices 107A-107C (e.g.,mobile phones, smart phones, PDAs, or the like) that are associated withone or more of a user (e.g., a delivery worker) or a vehicle (e.g., adelivery truck). In some embodiments, shipment and order tracking system111 may also request information from warehouse management system (WMS)119 to determine the location of individual products inside of afulfillment center (e.g., fulfillment center 200). Shipment and ordertracking system 111 may request data from one or more of transportationsystem 107 or WMS 119, process it, and present it to a device (e.g.,user devices 102A and 102B) upon request.

Fulfillment optimization (FO) system 113, in some embodiments, may beimplemented as a computer system that stores information for customerorders from other systems (e.g., external front end system 103 and/orshipment and order tracking system 111). FO system 113 may also storeinformation describing where particular items are held or stored. Forexample, certain items may be stored only in one fulfillment center,while certain other items may be stored in multiple fulfillment centers.In still other embodiments, certain fulfillment centers may be designedto store only a particular set of items (e.g., fresh produce or frozenproducts). FO system 113 stores this information as well as associatedinformation (e.g., quantity, size, date of receipt, expiration date,etc.).

FO system 113 may also calculate a corresponding PDD (promised deliverydate) for each product. The PDD, in some embodiments, may be based onone or more factors. For example, FO system 113 may calculate a PDD fora product based on a past demand for a product (e.g., how many timesthat product was ordered during a period of time), an expected demandfor a product (e.g., how many customers are forecast to order theproduct during an upcoming period of time), a network-wide past demandindicating how many products were ordered during a period of time, anetwork-wide expected demand indicating how many products are expectedto be ordered during an upcoming period of time, one or more counts ofthe product stored in each fulfillment center 200, which fulfillmentcenter stores each product, expected or current orders for that product,or the like.

In some embodiments, FO system 113 may determine a PDD for each producton a periodic basis (e.g., hourly) and store it in a database forretrieval or sending to other systems (e.g., external front end system103, SAT system 101, shipment and order tracking system 111). In otherembodiments, FO system 113 may receive electronic requests from one ormore systems (e.g., external front end system 103, SAT system 101,shipment and order tracking system 111) and calculate the PDD on demand.

Fulfillment messaging gateway (FMG) 115, in some embodiments, may beimplemented as a computer system that receives a request or response inone format or protocol from one or more systems in system 100, such asFO system 113, converts it to another format or protocol, and forward itin the converted format or protocol to other systems, such as WMS 119 or3^(rd) party fulfillment systems 121A, 121B, or 121C, and vice versa.

Supply chain management (SCM) system 117, in some embodiments, may beimplemented as a computer system that performs forecasting functions.For example, SCM system 117 may forecast a level of demand for aparticular product based on, for example, based on a past demand forproducts, an expected demand for a product, a network-wide past demand,a network-wide expected demand, a count products stored in eachfulfillment center 200, expected or current orders for each product, orthe like. In response to this forecasted level and the amount of eachproduct across all fulfillment centers, SCM system 117 may generate oneor more purchase orders to purchase and stock a sufficient quantity tosatisfy the forecasted demand for a particular product.

Warehouse management system (WMS) 119, in some embodiments, may beimplemented as a computer system that monitors workflow. For example,WMS 119 may receive event data from individual devices (e.g., devices107A-107C or 119A-119C) indicating discrete events. For example, WMS 119may receive event data indicating the use of one of these devices toscan a package. As discussed below with respect to fulfillment center200 and FIG. 2, during the fulfillment process, a package identifier(e.g., a barcode or RFID tag data) may be scanned or read by machines atparticular stages (e.g., automated or handheld barcode scanners, RFIDreaders, high-speed cameras, devices such as tablet 119A, mobiledevice/PDA 1198, computer 119C, or the like). WMS 119 may store eachevent indicating a scan or a read of a package identifier in acorresponding database (not pictured) along with the package identifier,a time, date, location, user identifier, or other information, and mayprovide this information to other systems (e.g., shipment and ordertracking system 111).

WMS 119, in some embodiments, may store information associating one ormore devices (e.g., devices 107A-107C or 119A-119C) with one or moreusers associated with system 100. For example, in some situations, auser (such as a part- or full-time employee) may be associated with amobile device in that the user owns the mobile device (e.g., the mobiledevice is a smartphone). In other situations, a user may be associatedwith a mobile device in that the user is temporarily in custody of themobile device (e.g., the user checked the mobile device out at the startof the day, will use it during the day, and will return it at the end ofthe day).

WMS 119, in some embodiments, may maintain a work log for each userassociated with system 100. For example, WMS 119 may store informationassociated with each employee, including any assigned processes (e.g.,unloading trucks, picking items from a pick zone, rebin wall work,packing items), a user identifier, a location (e.g., a floor or zone ina fulfillment center 200), a number of units moved through the system bythe employee (e.g., number of items picked, number of items packed), anidentifier associated with a device (e.g., devices 119A-119C), or thelike. In some embodiments, WMS 119 may receive check-in and check-outinformation from a timekeeping system, such as a timekeeping systemoperated on a device 119A-119C.

3^(rd) party fulfillment (3PL) systems 121A-121C, in some embodiments,represent computer systems associated with third-party providers oflogistics and products. For example, while some products are stored infulfillment center 200 (as discussed below with respect to FIG. 2),other products may be stored off-site, may be produced on demand, or maybe otherwise unavailable for storage in fulfillment center 200. 3PLsystems 121A-121C may be configured to receive orders from FO system 113(e.g., through FMG 115) and may provide products and/or services (e.g.,delivery or installation) to customers directly. In some embodiments,one or more of 3PL systems 121A-121C may be part of system 100, while inother embodiments, one or more of 3PL systems 121A-121C may be outsideof system 100 (e.g., owned or operated by a third-party provider).

Fulfillment Center Auth system (FC Auth) 123, in some embodiments, maybe implemented as a computer system with a variety of functions. Forexample, in some embodiments, FC Auth 123 may act as a single-sign on(SSO) service for one or more other systems in system 100. For example,FC Auth 123 may enable a user to log in via internal front end system105, determine that the user has similar privileges to access resourcesat shipment and order tracking system 111, and enable the user to accessthose privileges without requiring a second log in process. FC Auth 123,in other embodiments, may enable users (e.g., employees) to associatethemselves with a particular task. For example, some employees may nothave an electronic device (such as devices 119A-119C) and may insteadmove from task to task, and zone to zone, within a fulfillment center200, during the course of a day. FC Auth 123 may be configured to enablethose employees to indicate what task they are performing and what zonethey are in at different times of day.

Labor management system (LMS) 125, in some embodiments, may beimplemented as a computer system that stores attendance and overtimeinformation for employees (including full-time and part-time employees).For example, LMS 125 may receive information from FC Auth 123, WMA 119,devices 119A-119C, transportation system 107, and/or devices 107A-107C.

The particular configuration depicted in FIG. 1A is an example only. Forexample, while FIG. 1A depicts FC Auth system 123 connected to FO system113, not all embodiments require this particular configuration. Indeed,in some embodiments, the systems in system 100 may be connected to oneanother through one or more public or private networks, including theInternet, an Intranet, a WAN (Wide-Area Network), a MAN(Metropolitan-Area Network), a wireless network compliant with the IEEE802.11a/b/g/n Standards, a leased line, or the like. In someembodiments, one or more of the systems in system 100 may be implementedas one or more virtual servers implemented at a data center, serverfarm, or the like.

FIG. 2 depicts a fulfillment center 200. Fulfillment center 200 is anexample of a physical location that stores items for shipping tocustomers when ordered. Fulfillment center (FC) 200 may be divided intomultiple zones, each of which are depicted in FIG. 2. These “zones,” insome embodiments, may be thought of as virtual divisions betweendifferent stages of a process of receiving items, storing the items,retrieving the items, and shipping the items. So while the “zones” aredepicted in FIG. 2, other divisions of zones are possible, and the zonesin FIG. 2 may be omitted, duplicated, or modified in some embodiments.

Inbound zone 203 represents an area of FC 200 where items are receivedfrom sellers who wish to sell products using system 100 from FIG. 1A.For example, a seller may deliver items 202A and 202B using truck 201.Item 202A may represent a single item large enough to occupy its ownshipping pallet, while item 202B may represent a set of items that arestacked together on the same pallet to save space.

A worker will receive the items in inbound zone 203 and may optionallycheck the items for damage and correctness using a computer system (notpictured). For example, the worker may use a computer system to comparethe quantity of items 202A and 202B to an ordered quantity of items. Ifthe quantity does not match, that worker may refuse one or more of items202A or 202B. If the quantity does match, the worker may move thoseitems (using, e.g., a dolly, a handtruck, a forklift, or manually) tobuffer zone 205. Buffer zone 205 may be a temporary storage area foritems that are not currently needed in the picking zone, for example,because there is a high enough quantity of that item in the picking zoneto satisfy forecasted demand. In some embodiments, forklifts 206 operateto move items around buffer zone 205 and between inbound zone 203 anddrop zone 207. If there is a need for items 202A or 202B in the pickingzone (e.g., because of forecasted demand), a forklift may move items202A or 202B to drop zone 207.

Drop zone 207 may be an area of FC 200 that stores items before they aremoved to picking zone 209. A worker assigned to the picking task (a“picker”) may approach items 202A and 202B in the picking zone, scan abarcode for the picking zone, and scan barcodes associated with items202A and 202B using a mobile device (e.g., device 119B). The picker maythen take the item to picking zone 209 (e.g., by placing it on a cart orcarrying it).

Picking zone 209 may be an area of FC 200 where items 208 are stored onstorage units 210. In some embodiments, storage units 210 may compriseone or more of physical shelving, bookshelves, boxes, totes,refrigerators, freezers, cold stores, or the like. In some embodiments,picking zone 209 may be organized into multiple floors. In someembodiments, workers or machines may move items into picking zone 209 inmultiple ways, including, for example, a forklift, an elevator, aconveyor belt, a cart, a handtruck, a dolly, an automated robot ordevice, or manually. For example, a picker may place items 202A and 202Bon a handtruck or cart in drop zone 207 and walk items 202A and 202B topicking zone 209.

A picker may receive an instruction to place (or “stow”) the items inparticular spots in picking zone 209, such as a particular space on astorage unit 210. For example, a picker may scan item 202A using amobile device (e.g., device 119B). The device may indicate where thepicker should stow item 202A, for example, using a system that indicatean aisle, shelf, and location. The device may then prompt the picker toscan a barcode at that location before stowing item 202A in thatlocation. The device may send (e.g., via a wireless network) data to acomputer system such as WMS 119 in FIG. 1A indicating that item 202A hasbeen stowed at the location by the user using device 1196.

Once a user places an order, a picker may receive an instruction ondevice 119B to retrieve one or more items 208 from storage unit 210. Thepicker may retrieve item 208, scan a barcode on item 208, and place iton transport mechanism 214. While transport mechanism 214 is representedas a slide, in some embodiments, transport mechanism may be implementedas one or more of a conveyor belt, an elevator, a cart, a forklift, ahandtruck, a dolly, a cart, or the like. Item 208 may then arrive atpacking zone 211.

Packing zone 211 may be an area of FC 200 where items are received frompicking zone 209 and packed into boxes or bags for eventual shipping tocustomers. In packing zone 211, a worker assigned to receiving items (a“rebin worker”) will receive item 208 from picking zone 209 anddetermine what order it corresponds to. For example, the rebin workermay use a device, such as computer 119C, to scan a barcode on item 208.Computer 119C may indicate visually which order item 208 is associatedwith. This may include, for example, a space or “cell” on a wall 216that corresponds to an order. Once the order is complete (e.g., becausethe cell contains all items for the order), the rebin worker mayindicate to a packing worker (or “packer”) that the order is complete.The packer may retrieve the items from the cell and place them in a boxor bag for shipping. The packer may then send the box or bag to a hubzone 213, e.g., via forklift, cart, dolly, handtruck, conveyor belt,manually, or otherwise.

Hub zone 213 may be an area of FC 200 that receives all boxes or bags(“packages”) from packing zone 211. Workers and/or machines in hub zone213 may retrieve package 218 and determine which portion of a deliveryarea each package is intended to go to, and route the package to anappropriate camp zone 215. For example, if the delivery area has twosmaller sub-areas, packages will go to one of two camp zones 215. Insome embodiments, a worker or machine may scan a package (e.g., usingone of devices 119A-119C) to determine its eventual destination. Routingthe package to camp zone 215 may comprise, for example, determining aportion of a geographical area that the package is destined for (e.g.,based on a postal code) and determining a camp zone 215 associated withthe portion of the geographical area.

Camp zone 215, in some embodiments, may comprise one or more buildings,one or more physical spaces, or one or more areas, where packages arereceived from hub zone 213 for sorting into routes and/or sub-routes. Insome embodiments, camp zone 215 is physically separate from FC 200 whilein other embodiments camp zone 215 may form a part of FC 200.

Workers and/or machines in camp zone 215 may determine which routeand/or sub-route a package 220 should be associated with, for example,based on a comparison of the destination to an existing route and/orsub-route, a calculation of workload for each route and/or sub-route,the time of day, a shipping method, the cost to ship the package 220, aPDD associated with the items in package 220, or the like. In someembodiments, a worker or machine may scan a package (e.g., using one ofdevices 119A-119C) to determine its eventual destination. Once package220 is assigned to a particular route and/or sub-route, a worker and/ormachine may move package 220 to be shipped. In exemplary FIG. 2, campzone 215 includes a truck 222, a car 226, and delivery workers 224A and224B. In some embodiments, truck 222 may be driven by delivery worker224A, where delivery worker 224A is a full-time employee that deliverspackages for FC 200 and truck 222 is owned, leased, or operated by thesame company that owns, leases, or operates FC 200. In some embodiments,car 226 may be driven by delivery worker 224B, where delivery worker224B is a “flex” or occasional worker that is delivering on an as-neededbasis (e.g., seasonally). Car 226 may be owned, leased, or operated bydelivery worker 224B.

According to an aspect of the present disclosure, computer-implementedsystem for managing inventory may comprise one or more memory devicesstoring instructions, and one or more processors configured to executethe instructions to perform operations. In some embodiments, thedisclosed functionality and systems may be implemented as part of one ormore of FO system 113 or WMS 119. The preferred embodiment comprisesimplementing the disclosed functionality and systems on warehousemanagement system 119, but one of ordinary skill will understand thatother implementations are possible.

Warehouse management system 119 may transmit a request to deliveryworkers 224A and 224B to pick up a return item from a customer and placethe return item in a return center when the customer requests a returnonline with a reason for return. The reason for return may include, butnot limited to, a broken item, wrong item size or wrong product shipped,customers changed their mind after item purchased, producing did notmatch the website or catalog description, the customer ordered the wrongproduct or item, excessive amount, the customer found better productprice elsewhere, late delivery of items, product is no longer needed,product did not meet customer expectations, etc. If the return item isin good condition for resale, warehouse management system 119 maytransfer the return item from the return center to a fulfillment forresale.

While embodiments of the present disclosure relate to scanning aone-dimensional barcode in order to capture identifiers, one of ordinaryskill will understand that other data capture implementations (e.g.,using QR code, RFID tags, NFC communication, etc.) are possible.

FIG. 3 is an exemplary flow chart of process 300 for generatingidentifiers to transfer at least one return item from a return center tofulfillment center 200. While FIG. 3 is described with respect to amobile device associated with a return center and warehouse managementsystem 119, one of ordinary skill in the art will recognize that otherconfigurations are possible. For example, a mobile device associatedwith a return center may be a return center system or any othercomputer-implemented devices capable of handling steps described below.

In step 301, a mobile device associated with a return center maytransmit a return item identifier and a request for a return identifierto warehouse management system 119. For example, a worker associatedwith a mobile device, which is associated with a return center, may scana barcode, affixed to a return item, associated with a return itemidentifier and the mobile device may transmit the return item identifierto warehouse management system 119 along with a request for a returnidentifier.

In step 302, warehouse management system 119 may receive the transmittedreturn item identifier and the request for a return identifier sent instep 301. The requested identifiers may be printed in the form ofbarcodes and affixed to a tote storing the return item associated withthe return item identifier but one of ordinary skill in the art willrecognize that identifiers may be in other forms.

In step 303, warehouse management system 119 may predict a zone within afulfillment center for stowing the return item associated with thereceived return item identifier. By way of example, warehouse managementsystem 119 may determine a target fulfillment center by requesting FOsystem 113 to provide a fulfillment center which stores the return itemassociated with the received return item identifier by transmitting thereturn item identifier to the FO system 113 because FO system 113 maystore information describing where particular items are held or storedas discussed above with respect to FIG. 1A. FO system 113 may find afulfillment center storing an item identical to the return item andprovide the fulfillment center to warehouse management system 119. Basedon the determined fulfillment center, warehouse management system 119may predict a zone within the determined fulfillment center for stowingthe return item associated with the return item identifier. Warehousemanagement system 119 may also predict a stowing capacity at thepredicted zone. By way of example, warehouse management system 119 maypredict a zone for stowing the return item based on one or moreparameters associated with the return item identifier associated withthe return item. For instance, warehouse management system 119 maypredict the zone for stowing the return item based on an algorithm thataggregates and weighs one or more parameters associated with the returnitem identifier associated with the return item. One or more parametersassociated with the return item identifier may comprise at least one ofa priority level of the return item identifier, a dimension of thereturn item associated with the return item identifier, a volume of thereturn item associated with the return item identifier, a weight of thereturn item associated with the return item identifier, a temperature inwhich the return item associated with the return item identifier needsto be stored, a return item grade associated with the return itemidentifier, or an expiration date of the return item associated with thereturn item identifier. One or more of these parameters may be used topredict the zone for stowing the return item. By way of example, allreturn item identifiers with a first return item grade and a volumegreater than 100,000 cm³ may be directed to a particular zone forstowing.

In step 305, warehouse management system 119 may generate a returnidentifier for the received return item identifier. The returnidentifier may identify the return item within the predicted fulfillmentcenter once the return item has been transferred to the predictedfulfillment center. For example, warehouse management system 119 maystore a return item contained in a tote received in fulfillment center200 as well as details associated with the return item in a databasestoring inventory within the fulfillment center 200. The returnidentifier may represent a number generated for a transfer from a returncenter to the predicted fulfillment center from step 303. The returnidentifier may further represent a statement including a plurality ofreturn items associated with the return identifiers. The returnidentifier may include at least one return item identifier which may bepresented as a stock keeping unit. The return identifier may replace awaybill number, a reservation number or purchase number associated witha new inbound item. The return identifier may enable a return itemassociated with the return identifier to be received by the predictedfulfillment center without going through processes forunloading/receiving a new item at fulfillment center 200.

In step 306, warehouse management system 119 may generate a toteidentifier associated with a tote containing the return item for stowingat the predicted zone within the predicted fulfillment center. Warehousemanagement system 119 may request FO system 113 to provide the toteidentifier associated with the predicted fulfillment center so a workerassociated with the predicted fulfillment center can stow return itemsin the tote at the predicted zone as soon as the tote is received.

In step 307, warehouse management system 119 may modify a database toassign the return item identifier to the generated return identifier andthe generated tote identifier associated with a tote containing at leastone return item, assign the predicted zone to the generated toteidentifier, assign the determined fulfillment center and the generatedtote identifier to the generated return identifier. For example, thestored return identifier may include the return item identifier, thestored tote identifier which further includes the return item identifierand the predicted zone, and the determined fulfillment center.

In step 308, warehouse management system 119 may transmit the generatedreturn identifier and the generated tote identifier to the mobile deviceassociated with the return center. For example, warehouse managementsystem 119 may transmit a user interface providing a generated returnidentifier from and a generated tote identifier from. In anotherexample, a warehouse management system 119 may transmit a request to aprinter, close to the mobile device associated with the return center,to print the generated return identifier and the tote identifier. Aworker associated with the mobile device may affix the printedidentifiers on a tote containing the return item.

In step 309, the mobile device associated with the return center mayreceive the transmitted return identifier and the transmitted toteidentifier sent in step 308. The mobile device may print the receivedreturn identifier and the received tote identifier and affix the printedidentifiers to a tote containing the return item. For example, themobile device may present a user interface of the transmitted returnidentifier and the transmitted tote identifier along with a button forprinting the identifiers.

Return items with identical return identifier and tote identifier may bestored in the same tote for a transfer from a return center to apredicted fulfillment center. The return identifier and the toteidentifier may be updated when new return item identifier generated theidentical return identifier and tote identifier. By updating the returnidentifier and the tote identifier, rather than generating new returnidentifier and new tote identifier, warehouse management system 119 mayneed less storage for keeping track of all generated identifiers thusimproving technology by saving resources such as storages. Once thereturn identifier and the tote identifier are updated, the updatedidentifiers may be transmitted to a mobile device associated with thereturn center and a worker associated with the mobile device may printand affix the updated identifiers on the tote containing return items.Warehouse management system 119 may not generate identical toteidentifier for items with identical return item identifiers.

FIG. 4 is an exemplary flow chart of process 400 for receiving atransferred return item at fulfillment center 200. While FIG. 4 isdescribed with respect to mobile device 1196 and warehouse managementsystem 119, one of ordinary skill in the art will recognize that otherconfigurations are possible.

In step 401, mobile device 119B may transmit a workstation identifier towarehouse management system 119. For example, a worker associated withmobile device 1196 may scan a workstation identifier in the form ofbarcode affixed to a workstation and the mobile device 119B mayautomatically transmit the workstation identifier to warehousemanagement system 119. An exemplary user interface for requesting aworkstation identifier is illustrated in FIG. 5A and will be describedin more detail.

In step 402, warehouse management system 119 may receive the workstationidentifier sent in step 401. The received workstation identifier mayindicate, for example, a worker associated with mobile device 1196 wantsto verify an assignment of the workstation to receive/unload a returnitem transferred from a return center.

In step 403, warehouse manage system 119 may retrieve stored workstationidentifiers. A workstation identifier is stored when it is assigned to amobile device associated with fulfillment center 200.

In step 404, warehouse manage system 119 may determine whether thereceived workstation identifier matches one of the retrieved workstationidentifiers from step 403. If the received workstation identifiermatches one of the retrieved workstation identifiers, a workstationassociated with the received workstation identifier may not be assignedto the mobile device 119B. Warehouse management system 119 may transmita message to mobile device 119B indicating the workstation is alreadyassigned and ask whether the system should override an assignment to themobile device 119B if the received workstation identifier matches one ofthe retrieved workstation identifiers. If mobile device 119B provided aninput to override the workstation assignment, warehouse managementsystem 119 may process steps described below with respect to when thereceived workstation identifier does not match. An exemplary userinterface for displaying an assignment of workstation and requesting foroverride of the assignment is illustrated in FIG. 5G and will bedescribed in more detail. If the received workstation identifier doesnot match one of the retrieved workstation identifiers or mobile device119B overrode the assignment of the workstation, then warehousemanagement system 119 may store the received workstation identifier instep 405 and transmit a request for a return item identifier and a toteidentifier to mobile device 119B in step 406.

In step 407, mobile device 119B may receive the request for a returnidentifier and a tote identifier sent in step 406. For example, themobile device 119B may present a user interface of the transmittedrequest. Exemplary interfaces are discussed below with respect to FIGS.5B and 5C.

In step 408, mobile device 119B may transmit a return identifier and atote identifier to warehouse management system 119. The returnidentifier and the tote identifier, as discussed above with respect toFIG. 3, provide information associated with one or more return items.

In step 409, warehouse management system 119 may receive the transmittedreturn identifier and the transmitted tote identifier sent in step 408.The received return identifier and the received tote identifier mayrefer to, for example, a generated return identifier from step 305 and agenerated tote identifier from step 306.

In step 410, warehouse management system 119 may retrieve, from thedatabase discussed above with respect to FIG. 3, a fulfillment centerassigned to the received return identifier and a predicted zone assignedto the received tote identifier and comparing both against a location ofthe second mobile. For example, warehouse management system 119 maycompare the retrieved fulfillment center against a location of mobiledevice 119B or the received workstation identifier to determine whetherthe tote was transferred to the correct fulfillment center. By way offurther example, warehouse management system 119 may determine whetherthe retrieved predicted zone corresponds to the fulfillment centerdetermined by the location of mobile device 119B or the receivedworkstation identifier.

In step 411, warehouse management system 119 may transmit a request forstowing return items in the tote associated with the received toteidentifier to the mobile device 119B based on the comparison. Forexample, warehouse management system 119 may transmit, to the mobiledevice 119B, a user interface requesting stowing return items containedin a tote along with a predicted zone for stowing the return itemsincluded in the tote identifier when it was generated from step 306 inFIG. 3.

In step 412, mobile device 119B may receive the request for stowingreturn items sent in step 412. For example, mobile device 119B maydisplay a message requesting stowing return items contained in a tote atpredicted zone.

In step 413, warehouse management system 119B may modify the database toassign a return item identifier, assigned to the received toteidentifier, to a predicted zone assigned to the received toteidentifier. By storing the return item identifier to the predicted zone,warehouse management system 119 may utilize a return item associatedwith the stored return item identifier as inventory within thefulfillment center 200 and enable customer to purchase the return item.

In step 414, mobile device 119B may process a stowing task. For example,a worker associated with mobile device 119B may stow the return item inthe predicted zone within the fulfillment center 200. When the stowingis complete, mobile device 119B may communicate to warehouse managementsystem 119 to cause the warehouse management system 119 to modify thedatabase to acknowledge that stowing is complete. During the stowingprocess, stowing error may occur. The stowing error may comprise atleast one of an overage or a shortage. When a physical quantity of theat least one product is less than an expected quantity of the at leastone product, the stowing error may comprise overage. When a physicalquantity of the at least one product is greater than an expectedquantity of the at least one product, the stowing error may compriseshortage. When the stowing error occurred, warehouse management system119 may communicate to a mobile device 119B associated with the returncenter to notify mobile device 119B that a problem occurred whilestowing return items in the tote prepared by a worker associated withthe mobile device 119B.

FIG. 5A depicts an exemplary user interface 500 of a mobile device 119Bfor requesting a workstation identifier in the form of a barcode affixedto a workstation. For example, a worker associated with mobile device119B may use the mobile device 119B to scan the barcode and the mobiledevice may transmit the workstation identifier to the warehousemanagement system 119. The transmitted workstation identifier may bereceived by warehouse management system 119 as discussed above withrespect to step 402 in FIG. 4. In some embodiment, once warehousemanagement system 119 assigns the workstation associated with theworkstation identifier to mobile device 119B, the next interface shownon mobile device 119B may include another interface, such as theinterface depicted in FIG. 5B.

FIG. 5B depicts an exemplary user interface 501 of a mobile device 119Bfor requesting a return identifier in the form of a barcode (RTOBarcode) affixed to a tote. For example, a worker associated with mobiledevice 119B may use the mobile device 119B to scan the RTO barcode andthe mobile device may transmit the return identifier to the warehousemanagement system 119. The transmitted return identifier may be receivedby warehouse management system 119 as discussed above with respect tostep 409 in FIG. 4. In some embodiments, once warehouse managementsystem 119 determines a tote associated with the received returnidentifier was transferred to correct fulfillment center, the nextinterface shown on mobile device 119B may include another interface,such as the interface depicted in FIG. 5C.

FIG. 5C depicts an exemplary user interface 502 of a mobile device 119Bfor requesting a tote identifier in the form of a barcode affixed to atote. For example, a worker associated with mobile device 119B may usethe mobile device 119B to scan the tote barcode and the mobile devicemay transmit the tote identifier to the warehouse management system 119.The transmitted return identifier may be received by warehousemanagement system 119 as discussed above with respect to step 409 inFIG. 4. In some embodiment, once warehouse management system 119determines a tote associated with the received tote identifiercorresponds to the received return identifier as discussed above withrespect to step 411 in FIG. 4, the next interface shown on mobile device119B may include another interface, such as the interface depicted inFIG. 5E. The exemplary user interface 502 may also include a button 503.Button 503, when pressed by a worker associated with the mobile device119B, may display information associated with return items associatedwith the return identifier. Exemplary interface FIG. 5D may depictinformation displayed on mobile device 119B when the button 503 ispressed.

FIG. 5D depicts an exemplary user interface 504 of a mobile device 119Bfor displaying information associated with return items associated witha return identifier affixed to a tote. The information may include, butnot limited to, an image of return item, a product name, and a returnidentifier in form of the stock keeping unit. The information mayprovide that unintended return item is placed in the tote to a user workassociated with the mobile device 119B. Then, the worker may transmit areturn item identifier to warehouse management system 119 along with amessage that unintended return item was placed in the tote. Uponreceiving the message and the transmitted return item identifier,warehouse management system 119 may transmit a message to the mobiledevice which placed return items in the tote in return center thatunintended item was placed in the tote and transferred to fulfillmentcenter 200.

FIG. 5E depicts an exemplary user interface 505 of a mobile device 1196for displaying a completion message for transferring a tote containingat least one return item from a return center to a fulfillment center.Along with the completion message, warehouse management system 1196 maystore at least one return item contained in the tote identifier in adatabase storing inventory within the fulfillment center.

FIG. 5F depicts an exemplary user interface 506 of a mobile device 1196for cancelling a process for receiving return items. The user interface506 may include a button 507, wherein the button 507 may generate apopup window 508 when the button 507 is pressed. The popup window 508may include selectable elements for stopping the receiving task or stopthe cancelling process.

FIG. 5G depicts an exemplary user interface 509 of a mobile device 1196for displaying a message when a workstation is already assigned toanother mobile device. When mobile device 119B transmit a workstationidentifier as discussed above with respect to FIG. 5A or step 402,warehouse management system 119 may determine whether the receivedworkstation matches one of stored workstation identifiers (associatedwith workstations already assigned to another mobile device). When theworkstation associated with the received workstation identifier isalready assigned to another mobile device, warehouse management system119 may transmit the user interface 509 to request an input from mobiledevice 1196 to assign the workstation to mobile device 1196 or not.

FIG. 5H depicts an exemplary user interface 510 of a mobile device 119Bfor cancelling the transmitted return identifier when the mobile device119B transmitted unintended return identifier to warehouse managementsystem 119. The user interface 510 may include a button 511, wherein thebutton 511, when pressed, cancels the transmitted return identifier thusenabling mobile device 119B to transmit a different return identifier.

FIG. 6 is an exemplary flow chart of process 600 for processing arequest for returning an item.

In step 601, a user device associated with a customer, transmits areturn request for an item the customer purchased with a return reasonto warehouse management system 1196 via external front end system 103.The return reason may include, but not limited to, a broken item, wrongitem size or wrong product shipped, customers changed their mind afteritem purchased, products did not match the website or catalogdescription, the customer ordered the wrong product or item, excessiveamount, the customer found better product price elsewhere, late deliveryof items, product is no longer needed, product did not meet customerexpectations, etc.

In step 602, warehouse management system 119 may transmit a pickuprequest to delivery workers 224A and 224B. The delivery workers may pickup the return item from the customer and transport it to a returncenter.

In step 603, warehouse management system 1196 may generate a return itemidentifier, to be affixed to the return item for transferring to afulfillment center for resale, based on the received return reason. Forexample, if a return reason associated with a return item indicates thatthe return item is in good condition for sale, without any damages tothe return item, warehouse management system 119B may classify thereturn item for transferring to a fulfillment center for resale, whereina process for transferring the return item from a return center tofulfillment center is described above with respect to FIGS. 3 and 4, andgenerate a return item identifier to be affixed to the return item.

In step 604 may transmit the generated return item identifier to amobile device associated with the return center. For example, warehousemanagement system 119 may transmit a user interface providing agenerated return item identifier. In another example, a warehousemanagement system 119 may transmit a request to a printer, close to themobile device associated with the return center, to print the generatedreturn item identifier. A worker associated with the mobile device mayaffix the printed return item identifier on the return item,

While the present disclosure has been shown and described with referenceto particular embodiments thereof, it will be understood that thepresent disclosure can be practiced, without modification, in otherenvironments. The foregoing description has been presented for purposesof illustration. It is not exhaustive and is not limited to the preciseforms or embodiments disclosed. Modifications and adaptations will beapparent to those skilled in the art from consideration of thespecification and practice of the disclosed embodiments. Additionally,although aspects of the disclosed embodiments are described as beingstored in memory, one skilled in the art will appreciate that theseaspects can also be stored on other types of computer readable media,such as secondary storage devices, for example, hard disks or CD ROM, orother forms of RAM or ROM, USB media, DVD, Blu-ray, or other opticaldrive media.

Computer programs based on the written description and disclosed methodsare within the skill of an experienced developer. Various programs orprogram modules can be created using any of the techniques known to oneskilled in the art or can be designed in connection with existingsoftware. For example, program sections or program modules can bedesigned in or by means of .Net Framework, .Net Compact Framework (andrelated languages, such as Visual Basic, C, etc.), Java, C++,Objective-C, HTML, HTML/AJAX combinations, XML, or HTML with includedJava applets.

One or more memory devices may store data and instructions used toperform one or more features of the disclosed embodiments. For example,memory may represent a tangible and non-transitory computer-readablemedium having stored therein computer programs, sets of instructions,code, or data to be executed by processor. Memory may include, forexample, a removable memory chip (e.g., EPROM, RAM, ROM, DRAM, EEPROM,flash memory devices, or other volatile or non-volatile memory devices)or other removable storage units that allow instructions and data to beaccessed by processor.

One or more memory devices may also include instructions that, whenexecuted by processor, perform operations consistent with thefunctionalities disclosed herein. Devices consistent with disclosedembodiments are not limited to separate programs or computers configuredto perform dedicated tasks. For example, memory may include one or moreprograms to perform one or more functions of the disclosed embodiments.

One or more processors may include one or more known processing devices,such as a microprocessor from the Pentium™ or Xeon™ family manufacturedby Intel™, the Turion™ family manufactured by AMD™, the “Ax” or “Sx”family manufactured by Apple™, or any of various processors manufacturedby Sun Microsystems. The disclosed embodiments are not limited to anytype of processor(s).

Moreover, while illustrative embodiments have been described herein, thescope of any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations and/or alterations as would be appreciated bythose skilled in the art based on the present disclosure. Thelimitations in the claims are to be interpreted broadly based on thelanguage employed in the claims and not limited to examples described inthe present specification or during the prosecution of the application.The examples are to be construed as non-exclusive. Furthermore, thesteps of the disclosed methods may be modified in any manner, includingby reordering steps and/or inserting or deleting steps. It is intended,therefore, that the specification and examples be considered asillustrative only, with a true scope and spirit being indicated by thefollowing claims and their full scope of equivalents.

What is claimed is:
 1. A computer-implemented system for managinginventory by re-stocking a return item in fulfillment centers,comprising: one or more memory devices storing instructions; and one ormore processors configured to execute the instructions to performoperations comprising: receiving, from a user device associated with acustomer, a return request and a reason for return; transmitting apickup request to a mobile device associated with a delivery worker topick up a return item associated with the return request and deliver thereturn item to a return center; generating a return item identifier tobe affixed to the return item if the return item is in condition ofresale; receiving, from a first mobile device associated with the returncenter, the return item identifier and a request for a return identifierto be affixed to a tote containing the return item for transferring to atarget fulfillment center, the target fulfillment center beingdetermined based on the received return item identifier; predicting azone within the target fulfillment center for stowing the return itemassociated with the received return item identifier and a stowingcapacity of the predicted zone; modifying a database to assign thereturn item identifier to the return identifier and a tote identifierassociated with the tote containing the return item; modifying thedatabase to assign the predicted zone to the tote identifier; modifyingthe database to assign the target fulfillment center and the toteidentifier to the return identifier; printing, from a printer associatedwith the return center, a tote identifier and the return identifier;transmitting, to the first mobile device, a request to affix the printedidentifiers on the tote; receiving, from a second mobile deviceassociated with the target fulfillment center, the return identifier,the tote identifier and a location of the second mobile device, whereinthe return identifier and the tote identifier are captured by the secondmobile device from the printed identifiers affixed to the totecontaining the return item; retrieving, from the database, the assignedtarget fulfillment center to the received return identifier and theassigned predicted zone to the received tote identifier and comparingboth against the received location of the second mobile device todetermine the tote was transferred to the correct target fulfillmentcenter; transmitting a request, to the second mobile device, to stow thereturn item in the tote in the predicted zone in the target fulfillmentcenter when the proper transfer was processed based on the comparison;and modifying the database to assign the return item identifier assignedto the received tote identifier to the predicted zone assigned to thereceived tote identifier.
 2. The computer-implemented system of claim 1,wherein the operations further comprise: receiving, from the secondmobile device associated with the target fulfillment center, aworkstation identifier; retrieving workstation identifiers; determiningwhether the received workstation identifier matches one of the retrievedworkstation identifiers; and when the received workstation identifiermatches one of the retrieved workstation identifiers: providing, forpresentation via the second mobile device, a user interface thatincludes a message indicating another device associated with a worker isworking on a workstation associated with the received workstationidentifier, and when the received workstation identifier does not matchone of the retrieved workstation identifiers: storing the receivedworkstation identifier, and transmitting, to the second mobile device, arequest for a return identifier and a tote identifier.
 3. Thecomputer-implemented system of claim 1, wherein the return identifierincludes one or more tote identifiers.
 4. The computer-implementedsystem of claim 1, wherein the operations further comprise: receiving,from the second mobile device, a return item identifier which is notincluded in the received return identifier; and transmitting, to thefirst mobile device, a user interface that includes a message indicatingthat an incorrect item is in the tote.
 5. The computer-implementedsystem of claim 1, wherein the item identifier associated with the atleast one item comprises a stock keeping unit (SKU) associated with theat least one item.
 6. The computer-implemented system of claim 1,wherein the operations further comprise: determining whether there areidentical return item identifiers among the received return itemidentifiers; and providing, for presentation via the first mobiledevice, a user interface that includes a message indicating return itemswith the identical return item identifiers cannot be placed in the tote.7. The computer-implemented system of claim 1, wherein the operationsfurther comprise providing, for presentation via the second mobiledevice, a user interface that includes a selectable interface elementfor cancelling the received return identifier.
 8. Thecomputer-implemented system of claim 2, wherein the user interface thatincludes a message indicating another device associated with a worker isworking on a workstation further comprises a selectable interfaceelement for assigning the workstation to the second mobile device.
 9. Acomputer-implemented method for managing inventory by transferringreturn items to fulfillment centers, comprising: receiving, from a userdevice associated with a customer, a return request and a reason forreturn; transmitting a pickup request to a mobile device associated witha delivery worker to pick up a return item associated with the returnrequest and deliver the return item to a return center; generating areturn item identifier to be affixed to the return item if the returnitem is in condition of resale; receiving, from a first mobile deviceassociated with the return center, the return item identifier and arequest for a return identifier to be affixed to a tote containing thereturn item for transferring to a target fulfillment center, the targetfulfillment center being determined based on the received return itemidentifier; predicting a zone within the target fulfillment center forstowing the return item associated with the received return itemidentifier and a stowing capacity of the predicted zone; modifying adatabase to assign the return item identifier to the return identifierand a tote identifier associated with the tote containing the returnitem; modifying the database to assign the predicted zone to the toteidentifier; modifying the database to assign the target fulfillmentcenter and the tote identifier to the return identifier; printing, froma printer associated with the return center, a tote identifier and thereturn identifier; transmitting, to the first mobile device, a requestto affix the printed identifiers on the tote; receiving, from a secondmobile device associated with the target fulfillment center, the returnidentifier, the tote identifier and a location of the second mobiledevice, wherein the return identifier and the tote identifier arecaptured by the second mobile device from the printed identifiersaffixed to the tote containing the return item; retrieving, from thedatabase, the assigned target fulfillment center to the received returnidentifier and the assigned predicted zone to the received toteidentifier and comparing both against the received location of thesecond mobile device to determine the tote was transferred to thecorrect target fulfillment center; transmitting a request, to the secondmobile device, to stow the return item in the tote in the predicted zonein the target fulfillment center when the proper transfer was processedbased on the comparison; and modifying the database to assign the returnitem identifier assigned to the received tote identifier to thepredicted zone assigned to the received tote identifier.
 10. The methodof claim 9, further comprising: receiving, from the second mobile deviceassociated with the target fulfillment center, a workstation identifier;retrieving workstation identifiers; determining whether the receivedworkstation identifier matches one of the retrieved workstationidentifiers; and when the received workstation identifier matches one ofthe retrieved workstation identifiers: providing, for presentation viathe second mobile device, a user interface that includes a messageindicating another device associated with a worker is working on aworkstation associated with the received workstation identifier, andwhen the received workstation identifier does not match one of theretrieved workstation identifiers: storing the received workstationidentifier, and transmitting, to the second mobile device, a request fora return identifier and a tote identifier.
 11. The method of claim 9,wherein the return identifier includes one or more tote identifiers. 12.The method of claim 9, further comprising: receiving, from the secondmobile device, a return item identifier which is not included in thereceived return identifier; and transmitting, to the first mobiledevice, a user interface that includes a message indicating that anincorrect item is in the tote.
 13. The method of claim 9, wherein theitem identifier associated with the at least one item comprises a stockkeeping unit (SKU) associated with the at least one item.
 14. The methodof claim 9, further comprising: determining whether there are identicalreturn item identifiers among the received return item identifiers; andproviding, for presentation via the first mobile device, a userinterface that includes a message indicating return items with theidentical return item identifiers cannot be placed in the tote.
 15. Themethod of claim 9, further comprising providing, for presentation viathe second mobile device, a user interface that includes a selectableinterface element for cancelling the received return identifier.
 16. Themethod of claim 10, wherein the user interface that includes a messageindicating another device associated with a worker is working on aworkstation further comprises a selectable interface element forassigning the workstation to the second mobile device.